Servers configuration
These settings are independently set for each IPS Server machine.
When there is more than one machine, use the tabs labelled by the machine names to select the required machine.
The purpose of these settings is:
- to control the allocation of resource-intensive processes to the different machines in a cluster, in particular so that machines with greater resources (CPU cores, memory) can be allocated a greater share of the processing load;
- for each machine, to control the relative allocation of resources to different categories of processes.
Workers settings
Worker processes are maintained by IPS Server to perform resource-intensive operations. You can set the number of workers which can run concurrently on a server machine, and how these workers can be allocated to different processing categories.
To change a setting, type a new value into an input field.
Use the red 'Reset' button to change the setting to its default value.
You must click 'Save all changes' at the top of the page to save the changes that you make.
Number of workers: You can set the maximum number of workers which can run concurrently on a server machine. The default number is 4.
Workers per processing category: You can set the maximum number of workers that will be allocated to a processing category (see the list below) at any time. The default number is 2.
Processor affinity per processing category: You can control which server CPU cores are usable by a worker process. The default is to use any of the cores except 'CPU0'.
These are the processing categories that can be controlled:
- Dataflow Bulk Load
- PalantirCASH Result Set Calculation
- PalantirFINANCIALS Result Set Calculation
- PlanningSpace Decline Database Load
- PlanningSpace Decline File Load
- PlanningSpace Economics Result Set Calculation
- PlanningSpace Financials Result Set Calculation
- PlanningSpace Reconciliation Creation and Loading
- PlanningSpace Report Generation
Scheduler thread pool settings
Type a new value for a setting into the input field.
Use the red 'Reset' button to change the setting to its default value.
You must click 'Save all changes' at the top of the page to save the changes that you make.
| Setting name | Description | Default Value | Allowed values or range |
|---|---|---|---|
| Server Tasks Pool Size | The maximum number of threads that can be allocated to server tasks on a server machine. | 48 | 0 to 2147483647 |
| Periodic Tasks Pool Size | The maximum number of threads that can be allocated to periodic tasks on a server machine. | 24 | 0 to 2147483647 |
Application processor affinity
You can separately control which server CPU cores are usable by each of the PlanningSpace (and suite CX) applications. The default is to use all of the cores except 'CPU0'.
Advanced settings
Use the 'Edit' button to change a setting value.
Use the red 'Reset' button to change the setting to its default value.
You must click 'Save all changes' at the top of the page to save the changes that you make.
| Setting name | Description | Default Value | Allowed values or range |
|---|---|---|---|
| Category: Diagnostics | |||
| LogFolder | Folder that will contain the PlanningSpace log files for the server machine. | C:\ProgramData\Palantir\PalantirIPS 16.4\Logs
(or 'PalantirIPS 16.4 SPn' where Service Pack n is installed) |
Any existing local file folder |
| DumpFolder | Folder that will contain the memory dump file in the event of unexpected shutdown of the IPS Server machine. | C:\ProgramData\Palantir\PalantirIPS 16.4\Dump
(or 'PalantirIPS 16.4 SPn' where Service Pack n is installed) |
Any existing local file folder |
| Category: Scheduler | |||
| Max Concurrent Tasks Per Job | Jobs use parallel tasks for some operations; this setting is the maximum allowed number of parallel tasks. | (Number of cores) - 1 | Integer, 1 to 2*Default (depending on the number of machine processor cores) |
| Category: Web Server | |||
| Web Request Processor Affinity | The processor affinity setting determines which CPU cores will be assigned when an application-specific web request is received, such as OData and Web API requests; the server must be restarted after changing the setting for the setting to take effect. See Integration Services (OData) for explanation. | Depends on the number of machine CPU cores. Default value is '0x2' for 2 cores, '0xE' for 4 cores, '0xFC' for 8 cores, '0xFFF0' for 16 cores. | Hexadecimal value. See Integration Services (OData) for explanation. |